|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 6507 (2012)
|
|
Title:
|
Elliptic Curve-Based Certificateless Signatures for Identity-Based Encryption (ECCSI)
|
|
|
2.
|
Status of approval:
|
|
|
February 2012 as Internet Standard.
|
|
3.
|
Justification for the specific reference:
|
|
|
EAP-TLS-IBS and EAP-PSK-ECCSI specified in Annex D of this document(x.ibc-iot) uses ECCSI signature algorithms and protocols specified in IETF RFC 6507
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Approved in February 2012 as informational.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
0 errata are available.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Not known.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
[ECDSA] X9.62-2005, "Public Key Cryptography for the Financial/
Services Industry: The Elliptic Curve Digital Signature/
Algorithm (ECDSA)", November 2005./
/
[FIPS186-3] Federal Information Processing Standards Publication/
(FIPS PUB) 186-3, "Digital Signature Standard (DSS)",/
June 2009./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC5480] Turner, S., Brown, D., Yiu, K., Housley, R., and T./
Polk, "Elliptic Curve Cryptography Subject Public Key/
Information", RFC 5480, March 2009./
/
[RFC6090] McGrew, D., Igoe, K., and M. Salter, "Fundamental/
Elliptic Curve Cryptography Algorithms", RFC 6090,/
February 2011./
/
/
/
Informative Reference/
/
[BA] Arazi, Benjamin, "Certification of DL/EC Keys", paper/
submitted to P1363 meeting, August 1998,/
http://grouper.ieee.org/groups/1363/StudyGroup//
contributions/arazi.doc./
/
[FIPS180-3] Federal Information Processing Standards Publication/
(FIPS PUB) 180-3, "Secure Hash Standard (SHS)",/
October 2008./
/
[RFC3830] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and/
K. Norrman, "MIKEY: Multimedia Internet KEYing",/
RFC 3830, August 2004./
/
[RFC4086] Eastlake 3rd, D., Schiller, J., and S. Crocker,/
"Randomness Requirements for Security", BCP 106,/
RFC 4086, June 2005./
/
[RFC6508] Groves, M., "Sakai-Kasahara Key Encryption (SAKKE)",/
RFC 6508, February 2012./
/
[RFC6509] Groves, M., "MIKEY-SAKKE: Sakai-Kasahara Key Encryption/
in Multimedia Internet KEYing (MIKEY)", RFC 6509,/
February 2012./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
